Red Deck
Cupid Stunts.
The Wolfpack Nexus
10
   |
Posted - 2013.09.05 21:23:00 -
[1] - Quote
Well, I have just installed Odyssey 1.1 almost without a hitch - but I will admit that had I not read through this whole thread, it might have been a very different experience.
There was one very weird thing going on throughout the patching process - and I strongly suggest everybody trying to install the patch checks whether it's happening on their machine too before he/she starts killing the launcher, running exefile.exe, deleting or repairing files, and whatnot (as I suspect THAT is when the REAL mess commences).
Simply put, rather randomly, the progress bar stops updating - however, the patching process is actually proceeding just fine. It's been mentioned several times in this thread, but I believe it's worth pointing out again. I have encountered several moments when the patching process seemed to hit a wall (first right when the update started, then several times later on) - seemingly no progress for many many seconds.
However, every single time, I have eventually managed to get the progress bar to start displaying the progress again (and found out the download/patching/whatever was proceeding just fine). IIRC, hovering the cursor over the launcher window always did the trick, but it was not the only way. Clicking around, minimizing the launcher window and bringing it back to desktop, launching some other piece of software like Calculator or Notepad and closing it... there seemed to be multiple ways to "return the focus" to the updater bar (specifically: I was able to get the updater bar to work even with the cursor outside the launcher window).
So, if you're patching and things seem to be stuck, first check they really are - the computer savvy capsuleers may check the list of running processes to see if there is any CPU activity from a familiar process or check network connections to see if there are actually packets coming in.
Though the simple fix for me has always been just wiggling the cursor around a bit and parking it inside the launcher window.
WHY this happens, I don't know... perhaps some invisible interaction with background processes (like an antivirus), perhaps the launcher launches a subprocess and doesn't claim the focus back.
Just my two cents. |